Fix sql.DB leaks in unit tests so that tests pass on vmware hgfs #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Individual unit tests were unsuccessfully removing './foo.db' (the error was ignored) due to resource leaks, which caused everything but the first unit test to fail on my vmware hgfs filesystem. Adding the relevant defer statements for
db.Close()
androws.Close()
removed the leaks so thatos.Remove()
actually works.Minor fix:
t.Errorf("foo:", err)
rewritten ast.Error("foo:", err)
The original, on error, yields:
Corrected statement output:
Minor fix: Fixed single erroneous error message for sql.Open()
Minor fix: Replaced
t.Error("..."); return
witht.Fatal("...")